{"id":1744,"date":"2021-01-29T08:34:37","date_gmt":"2021-01-29T08:34:37","guid":{"rendered":"https:\/\/www.miquido.com\/blog\/?p=1744"},"modified":"2023-11-13T13:04:37","modified_gmt":"2023-11-13T12:04:37","slug":"is-kotlin-multiplatform-the-future","status":"publish","type":"post","link":"https:\/\/www.miquido.com\/blog\/is-kotlin-multiplatform-the-future\/","title":{"rendered":"Is Kotlin Multiplatform the future of cross-platform development? Tips on how to get started"},"content":{"rendered":"\n<p>Nowadays, we can observe a trend in <a href=\"https:\/\/www.miquido.com\/mobile-app-development\/\">custom mobile app development<\/a> to release apps faster. There were many attempts to reduce the time of development by sharing common code parts among different platforms such as Android and iOS. Some solutions have already gained popularity, while others are still under development. Today, I\u2019d like to discuss one of the newest approaches from the second group &#8211; <strong>Kotlin Multiplatform Mobile (KMM for short).<\/strong><\/p>\n\n\n\n<h2>What is Kotlin Multiplatform Mobile?<\/h2>\n\n\n\n<p><strong>KMM is an SDK that primarily aims to share business logic among platforms <\/strong>&#8211; the part that in most cases has to be the same anyway. This is achieved thanks to a set of multiple compilers for a shared module. For example, Android target uses a Kotlin\/JVM variant, and for iOS there is a Kotlin\/Native one. A shared module can be then added to typical native app projects and developers responsible for UI can focus on delivering the best experience for users in an environment familiar to them &#8211; Android Studio for Android and Xcode for iOS. <\/p>\n\n\n\n<h2>Kotlin Multiplatform vs Flutter<\/h2>\n\n\n\n<p>Currently, one of the most popular cross-platform solutions is <a href=\"https:\/\/www.miquido.com\/flutter-development-company\/\" target=\"_blank\" rel=\"noreferrer noopener\">Flutter app development<\/a>. It is focused on the \u201cwrite one app and run it everywhere\u201d rule \u2013 which works, but only for simple apps. <strong>In real case scenarios, developers often have to write native code for each platform anyway to fill the gaps<\/strong>, for example, when some plugin is missing. With this approach, the app looks the same on different platforms, which sometimes is desirable, but in some cases, it can break specific design guidelines.<\/p>\n\n\n\n<p>While they may sound similar, Kotlin Multiplatform is not a cross-platform solution &#8211; it doesn\u2019t try to reinvent the wheel. Developers can still use tools they know and like. <strong>It just simplifies the process of reusing parts of code <\/strong>that previously should have been written multiple times, like making network requests, storing data and other business logic.<\/p>\n\n\n\n<h3>When to choose Kotlin Multiplatform over Flutter?<\/h3>\n\n\n\n<p>When dealing with projects sporting substantial existing codebases or libraries, Kotlin steps into the spotlight as a pivotal advantage. Here, developers can strategically introduce Kotlin Multiplatform modules, embarking on a gradual migration journey. This approach ensures a seamless transition, preserving the investments in well-established codebases while leveraging Kotlin&#8217;s interoperability. Kotlin Multiplatform is particularly well-suited for large-scale enterprise applications where maintaining consistency and reusability across platforms is paramount.<\/p>\n\n\n\n<p>Flutter excels in crafting visually appealing and consistent user interfaces with its Dart programming language. It creates a unified UI experience using its rendering engine and Dart language. The framework provides a comprehensive set of pre-built widgets, ensuring consistency in appearance and behaviour across different platforms. On the other hand, Kotlin Multiplatform focuses on maximizing code reuse and minimizing platform-specific implementations.&nbsp;<\/p>\n\n\n\n<p>In essence, while Kotlin Multiplatform and Flutter contribute significantly to the cross-platform development landscape, the decision-making process involves a thoughtful evaluation of project requisites and team capabilities. Kotlin Multiplatform&#8217;s strengths shine brightly in scenarios where enterprise-level consistency, codebase adaptability, and strategic migration approaches take precedence. At the same time, Flutter excels in projects where a seamless and visually consistent user interface across platforms is a primary concern.&nbsp;<\/p>\n\n\n\n<h2>Pros and cons of Kotlin Multiplatform<\/h2>\n\n\n\n<p><strong>Pros of KMM<\/strong>:<\/p>\n\n\n\n<ul>\n<li><strong>The developed app is 100% native for each platform<\/strong> &#8211; it is easy to integrate with currently used code and third party libraries<\/li>\n\n\n\n<li><strong>Easy to use<\/strong> &#8211; almost all <a href=\"https:\/\/www.miquido.com\/android-development-company\/\" target=\"_blank\" rel=\"noreferrer noopener\">Android developers<\/a> already use Kotlin, so there is very little additional knowledge required for them to get started&nbsp;<\/li>\n\n\n\n<li><strong>UI can be split for each target platform<\/strong> &#8211; the app will feel consistent with any given ecosystem<\/li>\n\n\n\n<li><strong>Shared logic<\/strong> allows developers to add new features and fix bugs on both operating systems at the same time<\/li>\n<\/ul>\n\n\n\n<p><strong>Cons of KMM<\/strong>:<\/p>\n\n\n\n<ul>\n<li>Many components are still in <a href=\"https:\/\/kotlinlang.org\/docs\/mobile\/kmm-evolution.html\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Alpha\/Beta stage<\/a> and potentially can be unstable or change in future<\/li>\n<\/ul>\n\n\n\n<h2>Which companies use KMM?<\/h2>\n\n\n\n<p>According to the <a href=\"https:\/\/kotlinlang.org\/lp\/mobile\/case-studies\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">official site<\/a>, companies are increasingly gaining interest in this technology and the list is continuously getting longer and longer. Among them, there are such well-known brands like Autodesk, VMWare, Netflix or Yandex.<\/p>\n\n\n\n<h2>How to get started with Kotlin Multiplatform?<\/h2>\n\n\n\n<p>The best place to dive for in-depth information is the <a href=\"https:\/\/kotlinlang.org\/docs\/mobile\/getting-started.html\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">official guide<\/a>, but in this article, I would like to show an example that is fairly simple, but more interesting than just a \u201cHello World\u201d, which would be app fetching and displaying the latest <a href=\"https:\/\/xkcd.com\/2378\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">comic<\/a> by Randall Munroe (licensed under <a href=\"https:\/\/creativecommons.org\/licenses\/by-nc\/2.5\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">CC BY-NC 2.5<\/a>) with its title from xkcd.com <a href=\"https:\/\/xkcd.com\/json.html\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">API<\/a>.&nbsp;<\/p>\n\n\n\n<p>Features to be covered:<\/p>\n\n\n\n<ul>\n<li>Project setup<\/li>\n\n\n\n<li>Networking in the shared module<\/li>\n\n\n\n<li>Simple UI for both Android and iOS<\/li>\n<\/ul>\n\n\n\n<p>Note: I wanted this sample to be as easy to read for both Android and iOS developers, so in some places I intentionally omitted some platform-specific good practises just to make it clear what is going on \ud83d\ude42<\/p>\n\n\n\n<h3>Project setup<\/h3>\n\n\n\n<p>First, <strong>make sure you have the latest versions of Android Studio and Xcode<\/strong> installed because both of them will be necessary for the build of this project. Then, in Android Studio, install the KMM <a href=\"https:\/\/plugins.jetbrains.com\/plugin\/14936-kotlin-multiplatform-mobile\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">plugin<\/a>. This plugin simplifies a lot of things &#8211; to create a new project, just click Create New Project and select KMM Application.<br><\/p>\n\n\n\n<figure class=\"wp-block-image is-resized\"><img decoding=\"async\" src=\"https:\/\/lh4.googleusercontent.com\/BGvvCak65G_Uz5N59XcuNnVSTa5wZXVEZGRK01jAQCdVcMAMzUyrTMyUaDEH7cG_T4BNMVoYaNYF8A7XItIuA2blaH5za3EWbz8jHkePGv_Jt2_PrZ6eJ1X4gLkbzSv_jzSzaweo\" alt=\"Create a new Kotlin Multiplatform Mobile project\" width=\"726\" height=\"555\"\/><\/figure>\n\n\n\n<p>After the project is created, <strong>navigate to the <\/strong><code><strong>build.gradle.kts<\/strong><\/code><strong> file in the shared directory<\/strong>. Here you have to specify all required dependencies. In this example, we\u2019ll use ktor for the networking layer, <code>kotlinx.serialization<\/code> for parsing json responses from backend, and kotlin coroutines to do it all asynchronously. <\/p>\n\n\n\n<p>For simplicity, below I provide listings showing all dependencies that have to be added to the ones already present. When you add dependencies, just Sync the project (a prompt will appear). First, add the serialization plugin to the plugins section.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">plugins {\n   kotlin(\"plugin.serialization\") version \"1.4.0\"\n}<\/pre>\n\n\n\n<p>Then add dependencies.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sourceSets {\n   val commonMain by getting {\n       dependencies {\n           implementation(\"org.jetbrains.kotlinx:kotlinx-serialization-json:1.0.0\")\n           implementation(\"org.jetbrains.kotlinx:kotlinx-coroutines-core:1.3.9-native-mt-2\")\n\n           implementation(\"io.ktor:ktor-client-core:1.4.1\")\n           implementation(\"io.ktor:ktor-client-json:1.4.1\")\n           implementation(\"io.ktor:ktor-client-serialization:1.4.1\")\n       }\n   }\n   val androidMain by getting {\n       dependencies {\n           implementation(\"io.ktor:ktor-client-android:1.4.1\")\n       }\n   }\n   val iosMain by getting {\n       dependencies {\n           implementation(\"io.ktor:ktor-client-ios:1.4.1\")\n       }\n   }\n}<\/pre>\n\n\n\n<p>It\u2019s worth mentioning that at the time this article is being written, there are some problems with the stable version of coroutines library on iOS &#8211; that\u2019s why the version used has the native-mt-2 suffix (which stands for native multithreading). You can check the current status of this issue <a href=\"https:\/\/github.com\/kotlin\/kotlinx.coroutines\/issues\/462\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">here<\/a>.&nbsp;<\/p>\n\n\n\n<h3>Networking in the shared module<\/h3>\n\n\n\n<p>First, <strong>we need a class representing response<\/strong> &#8211; those fields are present in json returned by the backend.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">import kotlinx.serialization.Serializable\n\n@Serializable\ndata class XkcdResponse(\n   val img: String,\n   val title: String,\n   val day: Int,\n   val month: Int,\n   val year: Int,\n)<\/pre>\n\n\n\n<p>Next we need to <strong>create a class representing API with a HTTP client<\/strong>. In case we didn\u2019t provide all fields present in json, we can use the <code>ignoreUnknownKeys<\/code> property so the serializer can ignore missing ones. This example has only one endpoint represented by a suspended function. This modifier tells the compiler that this function is asynchronous. I\u2019ll describe it more with platform-specific code.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">import io.ktor.client.*\nimport io.ktor.client.features.json.*\nimport io.ktor.client.features.json.serializer.*\nimport io.ktor.client.request.*\n\nclass XkcdApi {\n   private val baseUrl = \"https:\/\/xkcd.com\"\n\n   private val httpClient = HttpClient() {\n       install(JsonFeature) {\n           serializer = KotlinxSerializer(\n               kotlinx.serialization.json.Json {\n                   ignoreUnknownKeys = true\n               }\n           )\n       }\n   }\n\n   suspend fun fetchLatestComic() =\n       httpClient.get&lt;XkcdResponse>(\"$baseUrl\/info.0.json\")\n\n}<\/pre>\n\n\n\n<p>When our network layer is ready, we can move to the domain layer and create a class representing the local model of data. In this example, I skipped some more fields and left just the comic title and URL to the image.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">data class ComicModel(\n   val imageUrl: String,\n   val title: String\n)<\/pre>\n\n\n\n<p>The last part for this layer is to create a use case which will trigger a network request and then map the response to the local model.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">class GetLatestComicUseCase(private val xkcdApi: XkcdApi) {\n   suspend fun run() = xkcdApi.fetchLatestComic()\n       .let { ComicModel(it.img, it.title) }\n}<\/pre>\n\n\n\n<h3>Simple UI for Android <\/h3>\n\n\n\n<p>Time to <strong>move to the <\/strong><code><strong>androidApp<\/strong><\/code><strong> directory<\/strong> &#8211; this is where the native Android app is stored. First, we need to<strong> add some Android-specific dependencies<\/strong> to the other <code>build.gradle.kts<\/code> file located here. Again, the listing below only shows dependencies that should be added to the ones already present. This app is going to use Model-View-ViewModel architecture (the first two lines), and <a href=\"https:\/\/github.com\/bumptech\/glide\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Glide<\/a> to load a comic image from the returned URL (the second two lines)<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">dependencies {\n   implementation(\"androidx.lifecycle:lifecycle-viewmodel-ktx:2.2.0\")\n   implementation(\"androidx.lifecycle:lifecycle-livedata-ktx:2.2.0\")\n   implementation(\"com.github.bumptech.glide:glide:4.11.0\")\n   annotationProcessor(\"com.github.bumptech.glide:compiler:4.11.0\")\n}<\/pre>\n\n\n\n<p>By default, a newly created project should contain MainActivity and its layout file <code>activity_main.xml<\/code>. Let\u2019s add some views to it &#8211; one <code>TextView<\/code> for title and one ImageView for the comic itself.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">&lt;?xml version=\"1.0\" encoding=\"utf-8\"?>\n&lt;LinearLayout xmlns:android=\"http:\/\/schemas.android.com\/apk\/res\/android\"\n   android:id=\"@+id\/main_view\"\n   android:layout_width=\"match_parent\"\n   android:layout_height=\"match_parent\"\n   android:gravity=\"center\"\n   android:orientation=\"vertical\">\n\n   &lt;TextView\n       android:id=\"@+id\/titleLabel\"\n       android:layout_width=\"wrap_content\"\n       android:layout_height=\"wrap_content\u201d\/>\n\n   &lt;ImageView\n       android:id=\"@+id\/image\"\n       android:layout_width=\"match_parent\"\n       android:layout_height=\"wrap_content\"\/>\n\n&lt;\/LinearLayout><\/pre>\n\n\n\n<p>Then <strong>we\u2019ll need some representation of the app state<\/strong> &#8211; it can be either loading a new comic, displaying it or we may encounter an error while loading.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">sealed class State {\n   object Loading : State()\n   class Success(val result: ComicModel) : State()\n   object Error : State()\n}<\/pre>\n\n\n\n<p>Now let\u2019s <strong>add a minimal ViewModel using the previously created business logic<\/strong>. All classes can be imported. <code>MutableLiveData<\/code> is an observable field &#8211; the view will observe changes to it and update itself accordingly. <code>viewModelScope<\/code> is a coroutine scope tied with the viewmodel&#8217;s lifecycle &#8211; in case the app is closed, it will automatically cancel pending tasks.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">class MainViewModel : ViewModel() {\n   private val getLatestComicUseCase = GetLatestComicUseCase(XkcdApi())\n   val comic = MutableLiveData&lt;State&lt;ComicModel>>()\n\n   fun fetchComic() {\n       viewModelScope.launch {\n           comic.value = State.Loading()\n           runCatching { getLatestComicUseCase.run() }\n               .onSuccess { comic.value = State.Success(it) }\n               .onFailure { comic.value = State.Error() }\n       }\n   }\n}<\/pre>\n\n\n\n<p>One last thing &#8211; MainActivity to wire everything up.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">class MainActivity : AppCompatActivity(R.layout.activity_main) {\n   private val viewModel: MainViewModel by lazy {\n      ViewModelProvider(this).get(MainViewModel::class.java)\n   }\n\n   override fun onCreate(savedInstanceState: Bundle?) {\n      super.onCreate(savedInstanceState)\n      viewModel.comic.observe(this) {\n         when(it) {\n            is State.Loading -> {\n               findViewById&lt;TextView>(R.id.titleLabel).text = \"Loading\"\n            }\n            is State.Success -> {\n               findViewById&lt;TextView>(R.id.titleLabel).text = it.result.title\n               Glide.with(this)\n                  .load(it.result.img)\n                  .into(findViewById(R.id.image))\n            }\n            is State.Error -> {\n               findViewById&lt;TextView>(R.id.titleLabel).text = \"Error\"\n            }\n         }\n      }\n      viewModel.fetchComic()\n   }\n}<\/pre>\n\n\n\n<p>That\u2019s it, the Android app is ready! <\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter is-resized\"><img decoding=\"async\" src=\"https:\/\/lh6.googleusercontent.com\/S6kj2dctAYyJ1EGtPsHTB3X9UsrrVMrO8tvUTMgDBJVJGkWDtLc0gnly26ibPh-I1qQxCp1HR-wnU7kUz49YHEakAkPnSZi5YQlqzD7mfipVoztSf14IEi8pjDHwUnkZH3d_ZQJb\" alt=\"An Android application developed with KMM\" width=\"402\" height=\"719\"\/><\/figure><\/div>\n\n\n<h3>Simple UI for iOS<\/h3>\n\n\n\n<p>Everything above was done in Android Studio, so for this part let\u2019s switch to Xcode to make it more convenient. To do this just <strong>open Xcode and select the iosApp directory<\/strong> &#8211; it contains a preconfigured Xcode project. By default this project uses SwiftUI for GUI so let\u2019s stick to it for simplicity\u2019s sake.<\/p>\n\n\n\n<p>The first thing to do is to create basic logic to fetch comic data. Just like before, we need something to represent state.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">enum State {\n    case loading\n    case success(ComicModel)\n    case error\n}<\/pre>\n\n\n\n<p>Next, let\u2019s prepare a ViewModel once more<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">class ViewModel: ObservableObject {\n    let getLatesteComicUseCase = GetLatestComicUseCase(xkcdApi: XkcdApi())\n        \n    @Published var comic = State.loading\n        \n    init() {\n        self.comic = .loading\n        getLatestComicUseCase.run { fetchedComic, error in\n            if fetchedComic != nil {\n                self.comic = .success(fetchedComic!)\n            } else {\n                self.comic = .error\n            }\n        }\n    }\n}<\/pre>\n\n\n\n<p>And, finally, the view. <\/p>\n\n\n\n<p>Note: for simplicity, I used SwiftUI component <a href=\"https:\/\/www.hackingwithswift.com\/forums\/swiftui\/loading-images\/3292\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">RemoteImage<\/a> to display the image, just like I used Glide on Android.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"kotlin\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">struct ContentView: View {\n \n    @ObservedObject private(set) var viewModel: ViewModel\n    \n    var body: some View {\n        comicView()\n    }\n    --\n    private func comicView() -> some View {\n        switch viewModel.comic {\n        case .loading:\n            return AnyView(Text(\"Loading\"))\n        case .result(let comic):\n            return AnyView(VStack {\n                Text(comic.title)\n                RemoteImage(url: comic.img)\n            })\n        case .error:\n            return AnyView(Text(\"Error\"))\n        }\n    }\n}<\/pre>\n\n\n\n<p>And that\u2019s it, the iOS app is also ready!<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter is-resized\"><img decoding=\"async\" src=\"https:\/\/lh4.googleusercontent.com\/QDyFzQERmmZgaVo2YLAHk4s-YohU1OmDRk4T_56JHN4tikMl85c7ChDtYwQl0JzeLqn1dDC4-fZ2bN2zYPDU9VCGGZWEPFQlbPqWV2QLUBb06rnqAsqaeO7e2gINg2P-7roQatl2\" alt=\"An iOS application developed with KMM\" width=\"477\" height=\"800\"\/><\/figure><\/div>\n\n\n<h2>Summary<\/h2>\n\n\n<section class=\"blog-paragraph-with-asset\">\n    <p>Finally, to answer the question from the title &#8211; <strong>Is Kotlin Multiplatform the future of cross-platform development? <\/strong>&#8211; it all depends on the needs. If you want to create a small, identical app for both mobile platforms at the same time, then probably not, <strong>because you need to have the required knowledge on development for both platforms.<\/strong><\/p>\n<\/section>\n\n\n<p>However, <strong>if you already have a team of Android and <a href=\"https:\/\/www.miquido.com\/ios-development-company\/\" target=\"_blank\" rel=\"noreferrer noopener\">iOS app developers<\/a> and want to deliver the best user experience, then it can significantly reduce development time<\/strong>. Like in the provided example, thanks to a shared module, application logic was implemented only once and the user interface was created in a fully platform-specific way. So why not give it a try? As you can see, it\u2019s easy to get started. <\/p>\n\n\n\n<p>Curious about cross-platform development from a business perspective? Check out our article on the <a href=\"https:\/\/www.miquido.com\/blog\/advantages-of-cross-platform-app-development-for-app-owners\/\" target=\"_blank\" rel=\"noreferrer noopener\">advantages of cross-platform development<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"Nowadays, we can observe a trend in custom mobile app development to release apps faster. There were many attempts to reduce the time of development by sharing common code parts among different platforms such as Android and iOS. Some solutions have already gained popularity, while others are still under development. Today, I\u2019d like to discuss [&hellip;]","protected":false},"author":40,"featured_media":13832,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"inline_featured_image":false,"_wp_applaud_exclude":false},"categories":[32],"tags":[70,75],"search-terms":[387,168,171,790,789,389,791,788,792,507],"coauthors":[94],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v20.9 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>What Is Kotlin Multiplatform Mobile: Definition, Pros and Cons - InfoSys Development<\/title>\n<meta name=\"description\" content=\"In this article, we explore all about Kotlin Multiplatform Mobile (KMM): what is it, how it&#039;s used and how to get started using it. Learn more about it!\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.miquido.com\/blog\/is-kotlin-multiplatform-the-future\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"What Is Kotlin Multiplatform Mobile: Definition, Pros and Cons - InfoSys Development\" \/>\n<meta property=\"og:description\" content=\"In this article, we explore all about Kotlin Multiplatform Mobile (KMM): what is it, how it&#039;s used and how to get started using it. Learn more about it!\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.miquido.com\/blog\/is-kotlin-multiplatform-the-future\/\" \/>\n<meta property=\"og:site_name\" content=\"InfoSys Development\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/miquido\/\" \/>\n<meta property=\"article:published_time\" content=\"2021-01-29T08:34:37+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-11-13T12:04:37+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.miquido.com\/wp-content\/uploads\/uploads\/2020\/07\/miquido-embeded.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Kamil D\u0119bi\u0144ski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@miquido\" \/>\n<meta name=\"twitter:site\" content=\"@miquido\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kamil D\u0119bi\u0144ski\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"What Is Kotlin Multiplatform Mobile: Definition, Pros and Cons - InfoSys Development","description":"In this article, we explore all about Kotlin Multiplatform Mobile (KMM): what is it, how it's used and how to get started using it. Learn more about it!","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.miquido.com\/blog\/is-kotlin-multiplatform-the-future\/","og_locale":"en_US","og_type":"article","og_title":"What Is Kotlin Multiplatform Mobile: Definition, Pros and Cons - InfoSys Development","og_description":"In this article, we explore all about Kotlin Multiplatform Mobile (KMM): what is it, how it's used and how to get started using it. Learn more about it!","og_url":"https:\/\/www.miquido.com\/blog\/is-kotlin-multiplatform-the-future\/","og_site_name":"InfoSys Development","article_publisher":"https:\/\/www.facebook.com\/miquido\/","article_published_time":"2021-01-29T08:34:37+00:00","article_modified_time":"2023-11-13T12:04:37+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.miquido.com\/wp-content\/uploads\/uploads\/2020\/07\/miquido-embeded.jpg","type":"image\/jpeg"}],"author":"Kamil D\u0119bi\u0144ski","twitter_card":"summary_large_image","twitter_creator":"@miquido","twitter_site":"@miquido","twitter_misc":{"Written by":"Kamil D\u0119bi\u0144ski","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.miquido.com\/blog\/is-kotlin-multiplatform-the-future\/","url":"https:\/\/www.miquido.com\/blog\/is-kotlin-multiplatform-the-future\/","name":"What Is Kotlin Multiplatform Mobile: Definition, Pros and Cons - InfoSys Development","isPartOf":{"@id":"https:\/\/www.miquido.com\/#website"},"datePublished":"2021-01-29T08:34:37+00:00","dateModified":"2023-11-13T12:04:37+00:00","description":"In this article, we explore all about Kotlin Multiplatform Mobile (KMM): what is it, how it's used and how to get started using it. Learn more about it!","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.miquido.com\/blog\/is-kotlin-multiplatform-the-future\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.miquido.com\/blog\/is-kotlin-multiplatform-the-future\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.miquido.com\/"},{"@type":"ListItem","position":2,"name":"Is Kotlin Multiplatform the future of cross-platform development? Tips on how to get started"}]},{"@type":"WebSite","@id":"https:\/\/www.miquido.com\/#website","url":"https:\/\/www.miquido.com\/","name":"InfoSys Development","description":"","publisher":{"@id":"https:\/\/www.miquido.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.miquido.com\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.miquido.com\/#organization","name":"InfoSys Development","url":"https:\/\/www.miquido.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.miquido.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.miquido.com\/wp-content\/uploads\/uploads\/2020\/07\/web3xlogo.png","contentUrl":"https:\/\/www.miquido.com\/wp-content\/uploads\/uploads\/2020\/07\/web3xlogo.png","width":121,"height":31,"caption":"InfoSys Development"},"image":{"@id":"https:\/\/www.miquido.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/miquido\/","https:\/\/twitter.com\/miquido","https:\/\/www.instagram.com\/miquido\/","https:\/\/www.linkedin.com\/company\/miquido"]}]}},"_links":{"self":[{"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/posts\/1744"}],"collection":[{"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/users\/40"}],"replies":[{"embeddable":true,"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/comments?post=1744"}],"version-history":[{"count":9,"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/posts\/1744\/revisions"}],"predecessor-version":[{"id":29599,"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/posts\/1744\/revisions\/29599"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/media\/13832"}],"wp:attachment":[{"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/media?parent=1744"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/categories?post=1744"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/tags?post=1744"},{"taxonomy":"search-terms","embeddable":true,"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/search-terms?post=1744"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.miquido.com\/wp-json\/wp\/v2\/coauthors?post=1744"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}